# Execution Reports Overview

## Introduction
Execution reports provide comprehensive insights into test runs, their outcomes, and detailed analysis of test execution results. This documentation covers the various aspects of execution reporting in Test Studio.

## Key Metrics

### Run Information
- **Run Date**: Date and time of test execution
- **Name**: Test case or suite name
- **Run Time**: Duration of test execution
- **Status**: Pass/Fail/Incomplete
- **Browser Type**: Browser used for execution
- **Log File**: Link to detailed execution logs

### Filtering Options
- **Application**: Filter by application
- **Component**: Filter by component/module
- **Test Scenario**: Filter by specific test case
- **Test Suite**: Filter by test suite
- **Clear Filter**: Reset all filters

## Report Actions

### View Options
- **View Test Case**: Navigate to test case details
- **View API Summary**: View API performance metrics
- **Run**: Execute selected test case
- **Analysis - Copilot**: AI-powered failure analysis

### Execution Management
- **Current Executions**: View active test runs
- **History**: Access execution history
  - Run Date
  - Run By (user)
  - Log File
  - Browser
  - Status
  - Error Code
  - Actions
  - Failure Analysis

## Best Practices
1. Regularly review execution reports
2. Monitor execution trends
3. Analyze failure patterns
4. Use filters effectively
5. Maintain execution history
6. Document common issues
7. Share insights with team